This repository has been archived by the owner on Jan 13, 2023. It is now read-only.
Fix error message in PromoteTransactionCommand
#313
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: #311
Description
Include the reason from the
infofield of theCheckConsistencyCommandresponse.This can be for example that the transaction is below max depth, the bundle is invlaid, or the transaction is not solid. This last one happens when one tries to immediately promote a transaction after it has just been broadcast and stored.
IRI Reference:
https://github.com/iotaledger/iri/blob/eb4e1a4409bbf74cc0198c5f2bd1a05524f81f4f/src/main/java/com/iota/iri/service/API.java#L388-L408